Skip to content

fix(geo): Record subregion name instead of M49 region code - #6049

Closed
mjq wants to merge 1 commit into
masterfrom
mjq/subregion
Closed

fix(geo): Record subregion name instead of M49 region code#6049
mjq wants to merge 1 commit into
masterfrom
mjq/subregion

Conversation

@mjq

@mjq mjq commented Jun 5, 2026

Copy link
Copy Markdown
Member

The sentry.user.geo.subregion attribute previously contained the M49 geographic region code - for example, if the user was located in Eastern Europe, the value of sentry.user.geo.subregion would be "151".

This isn't very usable, and is unlikely the actual semantics we want for this field when we create a new, non-sentry.-prefixed version of it for conventions.

Replace the value of this field with a string label for the detected region (so sentry.user.geo.subregion for a user in Eastern Europe would now be "Eastern Europe").

This is a breaking change if anyone is using this field in dashboards, alerts, etc.

@mjq mjq changed the title fix(geo): Record subregion as string instead of number fix(geo): Record subregion name instead of M49 region code Jun 5, 2026
@mjq
mjq force-pushed the mjq/subregion branch from 51e2266 to 3097ed9 Compare June 5, 2026 15:54
@mjq

mjq commented Jul 7, 2026

Copy link
Copy Markdown
Member Author

I'm going to close this - people aren't asking for it and I found some existing uses of the code. If we do this it would have to be in a backward compatible way.

@mjq mjq closed this Jul 7, 2026
@Dav1dde
Dav1dde deleted the mjq/subregion branch July 10, 2026 11:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant